Skip to content
This repository was archived by the owner on May 20, 2026. It is now read-only.

Fix skillContentRead and readFileToolInvoked telemetry in readFileTool#5051

Closed
AbhitejJohn wants to merge 1 commit into
microsoft:mainfrom
AbhitejJohn:aajohn/skill-content-read-telemetry
Closed

Fix skillContentRead and readFileToolInvoked telemetry in readFileTool#5051
AbhitejJohn wants to merge 1 commit into
microsoft:mainfrom
AbhitejJohn:aajohn/skill-content-read-telemetry

Conversation

@AbhitejJohn
Copy link
Copy Markdown
Contributor

Fixes skillContentRead telemetry to ensure each field has a proper prefix instead of using shorthand properties.\n\nAlso fixed readFileToolInvoked telemetry properties to use explicit key-value pairs instead of shorthand. Both events validated in local telemetry.

Fixes skillContentRead telemetry to ensure each field has a proper prefix.
Also fixed readFileToolInvoked telemetry properties to use explicit key-value
pairs instead of shorthand. Both events validated in local telemetry.
Copilot AI review requested due to automatic review settings April 9, 2026 20:19
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adjusts telemetry payload construction in the read_file tool to avoid shorthand object properties and ensure all telemetry fields are explicitly keyed, improving consistency/reliability of emitted event properties.

Changes:

  • Update readFileToolInvoked MSFT telemetry properties to use explicit key: value pairs.
  • Update skillContentRead GH/enhanced/internal telemetry properties to use explicit key: value pairs and consistently reference plaintextProps for contentHash.
Show a summary per file
File Description
src/extension/tools/node/readFileTool.tsx Makes telemetry event property objects explicit (no shorthand), aligning emitted keys with intended schema.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

@AbhitejJohn
Copy link
Copy Markdown
Contributor Author

ok, this isn't really required. The reason I wasn't seeing this earlier is because in Dev mode certain events weren't really flushed. Guided by Copilot, I made a local change to add a condition process.env['COPILOT_LOG_TELEMETRY'] === 'true' here and that got these events to flow through, not the changes in this PR. It would be nice to enhance dev mode for scenarios like these.

@AbhitejJohn AbhitejJohn closed this Apr 9, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants